Perform a retry when error code 3101 is returned from the MySQL DB #2583
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Go <gyakami@lycorp.co.jp>
Signed-off-by: Go <gyakami@lycorp.co.jp>
havetisyan
approved these changes
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We use MySQL as the storage for ZMS domain information. However, when using Group Replication with MySQL v8, there are cases where ErrorCode 3101 is returned in the response. The current implementation does not retry the DB update operation when a 3101 error is returned from the DB.
Therefore, we have made changes to perform a retry when a 3101 error is returned.
Contribution Checklist:
Attach Screenshots (Optional)